react-simplikit
[](https://www.npmjs.com/package/react-simplikit) [](https://github.com/toss/react-simplikit/blob/main/LICENSE) [: Transition to GitHub Actions publisher is intentional CI/CD automation; backed by SLSA provenance attestation from toss org. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.0.51 | 0 / 43 | |
| 0.0.50 | 0 / 43 | |
| 0.0.49 | 0 / 43 | |
| 0.0.48 | 0 / 43 | |
| 0.0.47 | 0 / 43 | |
| 0.0.46 | 0 / 41 | |
| 0.0.45 | 0 / 41 | |
| 0.0.43 | 0 / 41 | |
| 0.0.42 | 0 / 41 | |
| 0.0.40 | 0 / 41 | |
| 0.0.39 | 0 / 41 | |
| 0.0.38 | 0 / 41 | |
| 0.0.37 | 0 / 41 | |
| 0.0.36 | 0 / 41 |
v0.0.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.46
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.45
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.